home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
049a
/
ramail22.zip
/
RAMAIL.DOC
< prev
next >
Wrap
Text File
|
1991-03-16
|
19KB
|
419 lines
RAMail DOOR 2.2
Copyright 1990, 1991 by Randy Blackmond
All Rights Reserved
Welcome to RAMail, the mail system exclusively for RemoteAccess!
This version will probably not work with any RA versions prior to 1.00.
THE DOOR
--------
The RAMail Door is only half of the complete system. The other half
is a reader. You, as a sysop, don't need a reader for your door to
function, but your users will so they can read and reply to the mail
in the packets the door produces. I recommend The Silly Little Mail
Reader, but Session Manager, Qmail or EZ-Reader will also work.
The RAMail Door accesses MOST of your RA system files. All reasonable
precautions have been taken to ensure that RAMail will not damage any of
these files, but it is recommended that you backup all of your BBS system
files before running the RAMail Door for the first time.
INSTALLATION
------------
The first thing you need to do is to create a RAMAIL.CFG file by running
the RAMCONF.EXE program. You must supply the name of the CFG file you wish
to create/edit on the command line with RAMCONF. The fields are described
below:
Sysop Name
Your Name
Registration Number
0 if unregistered or your registration number
BBS Code
This is a 8 character or less name that will be used to name your
QWK files.
Path to CONFIG.RA
Path to your RA system directory with a trailing \
Path to EXITINFO.BBS
This field is for multiple node boards. It allows you to have
multiple CFG files and tells RAMail where to look for the
node-specific files. If you run a single node system, this field
should be identical to the previous field.
Path to DSZ.COM
The full path and filename to DSZ.COM.
Path to PKZIP.EXE
The full path and filename to PKZIP.EXE
Path to PKUNZIP.EXE
The full path and filename to PKUNZIP.EXE
Path to RAUSER.DAT
This field is for multiple node boards. It allows all nodes to use
the same RAMail data file. If you run a single node system, you will
still need to fill this field appropriately.
Local Mail Directory
This field allows you to tell RAMail where you want QWK packets for
local logons to be placed. Local REP files are also expected to be
in this directory. A valid drive and directory is required.
Required Conferences
Lets you specifiy which, if any, of your message boards you wish to
force into your users QWK packets. Each board number should be
separated by a single space. If you do not wish to force any boards,
leave this field blank.
Local Msg Limit
The highest number of messages RAMail will include in a QWK generated
from a local logon.
300 Baud Msg Limit
The highest number of messages RAMail will include in a QWK generated
for a 300 baud caller.
1200 Baud Msg Limit
The highest number of messages RAMail will include in a QWK generated
for a 1200 baud caller.
2400 Baud Msg Limit
The highest number of messages RAMail will include in a QWK generated
for a 2400 baud caller.
9600 Baud Msg Limit
The highest number of messages RAMail will include in a QWK generated
for a 9600+ baud caller.
Default File EXT
The file extension you use on your BBS downloadable files, e.g. ZIP,
ARC, PAK, LZH, etc.
Enable File Downloads
Allows you to disable the [F]iles function of RAMail.
Enable Hi Bit Filter
If you run a FIDO board, you will want to enable this feature. Other-
wise, you can disable it. It replaces all characters in uploaded
messages that are above ASCII 127 with an asterisk (*).
Sec Lvl for PRVT Msgs
Anyone with a security level matching this field or higher will be
able to receive private mail addressed to anyone in their packets.
Force reply FROM name
This allows you to force imported messages from users to have the
name in the FROM field match the users' logon name.
There are 3 display files that are included in the QWK packet for the
offline readers. One is a welcome screen, one is a news screen and the
third is a goodbye screen. In previous versions of RAMail, the screens
used were your WELCOME.A*, NEWS.A* and GOODBYE.A* files. In this version,
your can elect to provide separate screens for the QWK packets. If you
choose to use this option, the file names you must use are HELLO, INFO
and BYE for the ASCII version and HELLOG, INFOG and BYEG for the Ansi
versions. These files, if used, must reside in the same directory as
RAMail. If these files are not found during packet creation, the BBS
screens will be used as before.
Code 7 Setup
------------
Put RAMAIL.EXE and RAMAIL.CFG in your RA system directory. The menu entry
for RAMail should be as follows:
Optional Data: RAMAIL.EXE RAMAIL.CFG *M
You should use RA's swapping to ensure there is enough memory for RAMail
to run. To do this put *M after RAMAIL.EXE RAMAIL.CFG on your Optional
Data line. Failure to do so will probably result in not enough memory
being available for RAMail to call PKZIP, PKUNZIP and DSZ.
Code 15 Setup
-------------
First, create a directory on your hard drive in which RAMail will reside.
Place the RAMAIL.EXE program and the RAMAIL.CFG files into that directory.
Create a batch file like the one below:
@echo off
cd \RA\RAMAIL
RAMAIL RAMAIL.CFG
cd \RA
Note that the name of the CFG file you created is passed to RAMAIL.EXE on
the command line. Also, ANSI.SYS or some facsimile must be loaded to
enable you to see the ANSI colors the door uses locally. Loading ANSI.SYS
is not necessary for successful operation of the door, however.
Place the batch file in your RA directory and add the door to your menu
the same way you add any level 15 door.
Please realize that the QWK mail packet format is based on the PCBoard
message standard. What RAMail is basically doing is translating your RA
messages into PCBoard messages. One annoyance that will probably occur
is that your board names (referred to as "conferences" in the PCBoard
world) will be truncated to 10 characters when listed in the readers since
that is the limit to conference names for PCBoard! You could let your
RAMail users suffer through this minor annoyance, rename your boards OR
set up RACONFS.LST.
RAMail will look in the current directory for a file named RACONFS.LST
to use when inserting conference names into the QWK packet. This allows
you to retain your 30 character board descriptions in RA and still have
short, meaningful names for your users' readers! The format of this file
follows (NO BLANK LINES):
Conf#
ConfName
Conf#
ConfName
etc...
Example:
1
Main Board
2
Games
3
Telecom
4
Private
NOTES
-----
The RAUSER.DAT file has changed formats from v2.1. Use the included
USRTRANS.EXE to update your RAUSER.DAT or just delete it and start fresh.
Also, place the included DOOR.ID in the same directory(s) as your
RAMAIL.CFG file(s).
If you are running under a network such as Novell or Lantastic and you
experience the problem of RAMail not executing PKZIP, PKUNZIP or DSZ
properly, there is an alternate version available that may solve this
problem for you. It is available as RAM22A.ZIP from my BBS.
USAGE
-----
The menu for RAMail is straightforward. You have 15 options: Conference
Selection, Download, Upload, Modify Last Read Pointer, File Areas, Page,
System Info, Bulletin Toggle, Transfer Protocol, Help, New Files, Express
Mail Run, Include New Files Toggle, Quit and Goodbye.
Conference Selection allows your users to decide which message boards they
wish to be included in their downloaded mail. It will display all available
message boards and allow them to pick which ones they want. The config-
uration the user chooses will be saved in a mini user file maintained by
RAMail. They can change their configuration at any time. Users will
not be allowed to choose boards for which they do not have a high enough
security level and/or a set Read Flag to read.
The Download option extracts all new mail for the configuration the user
has chosen and places them in a compressed ZIP packet and then invokes
a DSZ Zmodem send of the packet.
The Upload option invokes a DSZ Zmodem receive of a reply packet that
will be named [BBSCODE].REP. It will then UNZIP the packet and import
the replies to your message files where they will be available immediately
for reading.
The Modify Last Read Pointer option allows the user to change their last
read pointer. The option will not let the user set their point higher than
the highest numbered message in the system.
The File Areas option allows users to view your file lists and flag files
to be downloaded with their mail packet. Checking is done to ensure the
user has access to a given file area according to security level and flag
settings. Full support of LIMITS.CTL is provided automatically as well.
The maximum number of files a user can flag for download is 5. This option
can be disabled if the sysop chooses to do so.
The Page option allows the user to page the Sysop for a chat.
The System Info option displays message stats, total calls and last caller
information.
The Bulletin Toggle allows the user to enable/disable the inclusion of
new bulletins in his/her mail packet.
The Transfer Protocol option allows the user to select a download protocol
to be used when performing mail/file transfers. This option is initially
set to Zmodem for new users.
The Help option will display the file RAMAIL.HLP. You can use the included
file or create your own.
The New Files option will search all available file directories for files
newer than (or equal to) the date of the user's last call and list them to
the screen.
The Express Mail Run option will cause RAMail to create the mail packet
and then immediately send it. Upon completion of the transfer, the user
will be logged off.
The Include New Files Toggle option enables/disables the new files scan
that RAMail performs during packet creation.
The Quit option returns the user to the BBS.
The Goodbye option disconnects the caller and exits the door.
Users can select the board configuration they want by entering special
offline messages. If a message is addressed to RAMAIL or QMAIL the
subject will determine the configuration action to be taken. The choices
for the subject are as follows:
ADD - Adds a conference and selects all mail
ADD A - Adds a conference and selects all mail
ADD Y - Adds a conference and selects your mail only
ADD YA - Adds a conference and selects your mail and mail to All
DROP - Drops a conference
HISTORY
-------
1.0 Initial release of RAMail!
1.1 Increased the speed of the message export process TREMENDOUSLY!
200 message packets should be created in about 30 seconds or so.
Did away with the idea of conference pointers. There's just no
feasible way to do something like that with RA. The last read
message pointer will be read from the user's record upon entry
into RAMail and updated after downloading a packet.
1.2 This version was released as a fix for the problem of the last read
message pointer not being updated. Too bad it didn't fix it!
1.3 Discovered reason for the read pointer not being updated (I thought)
Added different message download limits for each baud rate (See
INSTALLATION). Added Hot Keys.
1.4 Finally! An enhancement version! The Configuration option has been
enhanced to allow the user to elect to receive only their mail and
mail addressed to All or All mail. Added the Modify Last Read
Pointer option. Added optional RACONFS.LST board name file. Last
Read Message Pointer problem was finally solved!
1.5 Stomped a few more bugs. Added FIDO Default Origin line support for
messages uploaded to an EchoMail board. Increased packet processing
speed even more. RA's message indexes are automatically updated by
RAMail when replies are uploaded. New RAMCONF program eases creation
and modification of your RAMAIL.CFG file(s). Added support for
multiple nodes. RAMail should now work properly on boards where the
message files reside in their own directory. Much more!
2.0 Still more bugs stomped. Should now be completely FIDO compatible.
Added Files feature, Your Mail Only mail selector, high ASCII filter
option for FIDO boards, Personal Mail support, New Files and New
Bulletins support, Default Protocol, Online Help, Goodbye from the
menu or after transfer and more!
2.01 Maintenance release. The message attributes set by RAMail were all
messed up resulting in such problems as imported EchoMail messages
not being marked as pending export and private messages not being
marked or recognized as private.
2.1 Added path for RAUSER.DAT in RAMCONF.EXE. This was to allow multiple
node systems to use the same RAUSER.DAT file for all nodes. Added
(S)elect All and (D)eselect All in the configuration option.
2.2 Added support for the DOOR.ID file that SLMR 2.0 will make use of.
Added offline mail configuration support. RAMail will write to your
system log(s) when mail/files are download/uploaded. Origin lines
are attached to incoming echo mail only if Echo Info is enabled in
your RACONFIG. Stomped a few bugs.
DISCLAIMER
----------
As stated before, all reasonable precautions have been take to ensure
that your system files will not be damaged, but if any damage does
occur caused by RAMail either directly or indirectly, I will not
be held responsible for such damages. USE THIS PRODUCT AT YOUR OWN RISK!
CREDITS
-------
This Door was written with JPDOOR 3.0 Copyright 1991 by Rod Hancock
PKZIP/PKUNZIP is Copyright 1989-1991 by PKWARE, Inc.
DSZ is Copyright 1991 by Omen Technology INC
QuickBBS is Copyright 1990 by The QuickBBS Group, Inc.
RemoteAccess is Copyright 1991 by Continental Software
Session Manager is copyright 1991 by Patrick Hart
EZ-Reader is copyright 1988-1991 by Thumper Technologies
Qmail is copyright 1987-1991 by Sparkware
Silly Little Mail Reader is copyright 1991 by Greg Hewgill and
Computer Techniques
And special thanks to my beta testers for their patience, support and
wonderful suggestions!
PROBLEMS & SUGGESTIONS
----------------------
Bug reports, problems, suggestions and comments can be made to Randy
Blackmond in the RIME/RelayNet Doors, Sysops, Shareware or RA conference
or call Randy's Basement BBS 1200/2400/9600 USR DS at (505) 589-0319.
If you call the BBS, don't be surprised to find PCBoard instead of RA! I
find the market for QuickBBS/RA software more open to new products. I
STRONGLY encourage users to give suggestions for new features they would
like to see implemented!
REGISTRATION
------------
Usage of the RAMail Door for longer than a 2 week evaluation period
requires that you register the product with the author. Failure to do
so violates Federal Copyright Laws and places you in a position to which
the author can pursue monetary damages in a court of law. Why risk it?
Register the software. Registration entitles you to free upgrades forever
and access to beta versions as they appear on my BBS.
To register the RAMail Door, you have two options. 1) Complete the
following form and mail it back to the author with a check or money order
made payable to Randy Blackmond for $25.00. 2) Call my board and register
with your Visa/MasterCard/American Express. If you use this option, you
will be given a Registration Number by my MC-Visa-AmEx Door that will
allow you to replace the "UNREGISTERED" notice with your name and your
board name. If you register by mail, you will need to create a user
account for me on your BBS and write in my password on the mail-in
registration form. I will call your board and give you your registration
number in a private message.
------------------------------------------------------------------------
Randy Blackmond
RR #1 Box 634 RAMail 2.2 Door Registration Form
Anthony, NM 88021
NAME: _______________________________ ADDRESS: ________________________
CITY, STATE, ZIP CODE : ________________________________________________
HOME VOICE PHONE: _____________________ BBS NAME: ______________________
BBS PHONE: _____________________ BAUD RATES SUPPORTED: _________________
RANDY'S PASSWORD: ______________
COMMENTS: ______________________________________________________________
________________________________________________________________________
________________________________________________________________________